Minimal verifiable compression using lz4_flex
#4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nuke-web3
force-pushed
the
n/initial-compression
branch
from
6eadfc8 to
d6e4f50
Compare
nuke-web3
force-pushed
the
n/initial-compression
branch
from
d6e4f50 to
fdd90cf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #3
MVP working LZ4 compression workflow - adds ~50% overhead on cycles mentioned in #2 and a ~30% reduction in data needed to publish to DA
106,872,539 cycles (w/ lz4_flex compression) / 73,629,685 cycles (w/o compression) = 1.4514871151,135,812 bytes (compressed) / 1,546,973 bytes (uncompressed) = 0.734215788